Sensitive Data Platform (SDP) Console 13.5 Release Notes

Release: 13.5

Release Date: 8.28.2025

 

Known Issues

None.

Enhancements

  1. Users can begin User Level Remediation activity immediately upon completion of results by target, once its scan is complete without regard to the completion status of all other targets in the scan.

  2. Users can now filter differential scan results. When viewing differential scan results, users can now use a “Search History” drop-down menu to filter results for the following: All Results (default), Scanned Results, Skipped Results.

  3. When Svc-Ingress is queueing data to Kafka and the error “FetchTopicFromKafka - Disconnected” is thrown, SDP automatically attempts renegotiate the connection for resiliency.

  4. When Svc-AgentController is queueing data to Kafka or reading data from Kafka and the error “Svc-SearchPersistence - Disconnected” is thrown, SDP automatically attempts renegotiate the connection for resiliency.

  5. When Svc-AgentController is queueing data to Kafka or reading data from Kafka, and the error “FetchTopicFromKafka - Disconnected” is thrown, SDP automatically attempts to renegotiate the connection for resiliency.

  6. Agent Status now displays an agent as offline based on recalculated formula of: (Now - Agent Last Status Time) > 2*(Agent Status Interval) = Offline.

  7. Custom reports (Dynamic SQL queries) now perform in-line with other reports, and load in a timely fashion.

  8. Added the ability to authenticate using a customer-configured Azure App for Exchange Online and OneDrive.

Bug Fixes

  1. Resolved an issue in which the User Locked field toggle did not function correctly. Also corrected the functionality of the User System Access checkbox field when editing a user account.

  2. Resolved an issue in which assigning the Spirion Default Policy to an agent removed the agent from all policies.

  3. Resolved an issue in which Differential Scanning does not skip unchanged files when scanning the same locations using different Target/Admin credentials.

  4. Resolved an issue in which a user configured a notification email to be received upon scan completion, but no email was received.

  5. Resolved an issue in which the User Locked field toggle switch on the User Management page is not functional.

  6. Resolved an issue which caused duplication of database maintenance tasks.

  7. Resolved an issue in which duplicate rows appear in the SearchHistory database.

  8. Resolved an issue in which Differential Scanning is enabled, but a scan location that is removed from scan results cannot be rediscovered.

  9. Resolved an issue in which a MIP Label action is configured in a playbook and the workflow action is executed on the agent but is not reflected in the Most Recent Action field in the Scan Results page, even when it was the last action executed.

  10. Resolved an issue in which duplicate rows appear in the SearchHistory database.

  11. Resolved an issue in which Svc-Reporting fails to start.

  12. Resolved an issue in which no notification email is received by a user when SDP is configured to send a notification upon scan completion.

  13. Manual Kafka confirmation for various services (Svc-SearchPersistence, Svc-SearchHistory, and Svc-IncidentPersistence) explicitly marks messages as complete, so data is not lost during error states.

  14. Resolved an issue in which SPIglass™ Dashboard does not update after results are purged from the console via data retention.

  15. Resolved an issue in which results are delayed in being imported due to processing of deferred totals.

  16. Resolved additional Kafka lag vector in the console.

  17. Resolved an issue in which sorting by column in a report causes data to shift and render the last column empty.

  18. Resolved ambiguous column name 'Hash' error during results import.

  19. Prevented Svc-SearchPersistence from ingesting results messages so data warehouse processes do not fail.

  20. Stored procedure modified to improve scan lag.

  21. Resolved an issue in which running distributed and local scans do not update the Scan Details page while Kafka lag grows.

  22. Resolved an issue in which import playbook trace timeouts slowed results importing considerably, causing significant Kafka lag.